Skip to content

Add runbook for VirtLauncherPodsStuckFailed alert#330

Merged
sradco merged 1 commit intokubevirt:mainfrom
sradco:add_runbook_for_VirtLauncherPodsStuckFailed
Dec 15, 2025
Merged

Add runbook for VirtLauncherPodsStuckFailed alert#330
sradco merged 1 commit intokubevirt:mainfrom
sradco:add_runbook_for_VirtLauncherPodsStuckFailed

Conversation

@sradco
Copy link
Collaborator

@sradco sradco commented Dec 14, 2025

What this PR does / why we need it:
Adds a runbook for VirtLauncherPodsStuckFailed alert

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #https://issues.redhat.com/browse/CNV-74773

Special notes for your reviewer:

Checklist

This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

Release note:

NONE

@kubevirt-bot kubevirt-bot added the dco-signoff: yes Indicates the PR's author has DCO signed all their commits. label Dec 14, 2025
@sradco sradco force-pushed the add_runbook_for_VirtLauncherPodsStuckFailed branch 2 times, most recently from 3f975ef to 4394603 Compare December 14, 2025 10:28
@sradco
Copy link
Collaborator Author

sradco commented Dec 14, 2025

@orenc1 @rabin-io please review this runbook, diagnosis and mitigation steps.

Signed-off-by: Shirly Radco <sradco@redhat.com>
@sradco sradco force-pushed the add_runbook_for_VirtLauncherPodsStuckFailed branch from 4394603 to a6ef2a6 Compare December 14, 2025 10:33
@sradco sradco merged commit f229f2c into kubevirt:main Dec 15, 2025
2 checks passed
github-actions bot pushed a commit that referenced this pull request Dec 15, 2025
…VirtLauncherPodsStuckFailed

Add runbook for VirtLauncherPodsStuckFailed alert
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dco-signoff: yes Indicates the PR's author has DCO signed all their commits. size/L

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants